Get participants

Retrieve a list of all participants in the group.

GET

https://api.wawp.net/v2/groups/{id}/participants?access_token=123456789&id=1234567890%40g.us&instance_id=123456789

Authentication Required

Test /v2/groups/{id}/participants endpoint

Supports

GET

No query parameters required

This endpoint doesn't expect data in the URL.

Scaling

Large groups return large arrays. Handle pagination or timeouts.

Roles

The response includes the role (admin, superadmin, participant) of each user.

Best practices

Cache the participant list and only update on 'participant_changed' events.
Use this to audit who is actually in the group vs your database.
Filter by role to find all admins quickly.

Demographic Intelligence: The Strategic Audit of Community Membership

In the orchestration of distributed human networks, understanding who is in the room is the foundation of engagement, security, and personalization. The Get Participants endpoint is your primary tool for Strategic Demographic Auditing and Population Mapping. It allows your automated systems to retrieve a comprehensive census of every JID (@c.us) currently associated with a specific WhatsApp group. Beyond a simple list of numbers, this endpoint provides the structural context required to differentiate between influencers (Admins), owners (Creators), and the general population, enabling your platform to tailor its logic to the specific hierarchy of the community.

For enterprise architects, the participant list is the Raw Material of Targeting. This guide explores the strategic imperatives of membership auditing and the governance of group identity.

🏗️ Architectural Philosophy: Retrieving the Population State

From a technical perspective, the Get Participants endpoint is a State Snapshot of a One-to-Many Mapping.

Key Architectural Objectives:

The Authority Matrix: Every participant object in the response includes critical boolean flags: isAdmin and isSuperAdmin (Creator). By retrieving this list, your system builds an "Authority Map," allowing it to know exactly which users have the power to Add or Remove others. This is essential for building moderated systems that respect the existing human power structure within the chat.
Real-Time Population Integrity: WhatsApp groups are fluid; members join and leave constantly. The Get Participants API provides a "Synchronized Baseline," ensuring that your system's internal record of the group's "Census" matches the ground truth on Meta's servers. This is critical for preventing "Ghost Messaging" to members who have already left or ignoring new members who have just arrived.
Decoupling Presence from Contacts: Your instance can see and list all participants in a group even if those users aren't in your official phone contact list. This "Native Discovery" is what allows business bots to interact with an unlimited number of customers without the friction of manual contact saving.

🚀 Strategic Use Case: Target Segmentation and Automated Whitelisting

The participant list is more than just a registry; it is a signal for automated business logic.

1. The "VIP Tier" Dynamic Segmentation

Your system can periodically audit the membership of high-value support groups. If it detects a specific "Power User" (identified by their JID in your CRM) is present in multiple groups, the system can automatically flag them for a "Premium Experience" or Promote them to a moderator role. This "Automated Meritocracy" ensures that your most important stakeholders are always recognized and empowered within your conversational ecosystem.

2. Forensic Auditing and Compliance Verification

In regulated sectors (like Healthcare or Finance), knowing who has access to a conversation is a legal requirement. Your system should perform a "Compliance Audit" every 24 hours. By calling the Get Participants endpoint and comparing the list against your internal "Authorized Stakeholder Whitelist," you can detect "Unauthorized Observers"—users who were added manually by a human but who shouldn't have access to sensitive data. The system can then automatically Remove them, maintaining your organization's regulatory posture.

3. Audience Synchronizing for Multi-Channel Orchestration

If you are running a combined Email and WhatsApp campaign, the Group Participant list is your "Source of Truth" for the WhatsApp segment. Your system can extract the JIDs, map them to email addresses in your CRM, and ensure that a user who receives a "Group Update" on WhatsApp also receives the detailed "Follow-up Report" via email. This cross-channel synchronization turns a simple chat group into a sophisticated, multi-touch engagement engine.

🔐 Administrative Mandate: Privacy and the Governance of Identity

Managing a list of human identifiers is a high-responsibility task that requires strict governance.

Protecting the "Digital Footprint"

Group participant lists are sensitive data. Your system should ensure that only authorized senior agents or specific automated controllers can access the raw participant data. In your platform's UI, consider masking parts of the phone number for regular agents, while allowing the "Master Logic" to use the full JID for routing and personalization. The Get Participants endpoint is the "Secure Feed" that your platform must protect.

Handling "Group Saturation" (Large Group Logic)

WhatsApp groups currently support up to 1,024 members. When your system retrieves a participant list for a group nearing this limit, the response can be large. Your backend infrastructure should be optimized to parse these arrays efficiently. We recommend implementing "Differential Updates"—comparing the new list with the previous one and only processing the changes (joins/leaves)—to minimize the database load and keep your targeting logic responsive.

🛡️ Operational Best Practices: Consistency and Reconciliation

The "Welcome Bot" Trigger: While the group.participants.update webhook is great for real-time events, the Get Participants endpoint is your "Reconciliation Guardrail." If your system is unsure about a user's current status, a single GET call provides the definitive answer.
Staggered Audits: For organizations managing thousands of groups, avoid auditing every participant list at the same time. Stagger your audits over a 24-hour cycle to distribute the API load and ensure a consistent flow of demographic intelligence.
Integrity Checks after Migration: If you move your business logic from one WhatsApp account to another, use the Get Participants API to "Verify the Handover." Ensure that all members from the old groups have been successfully onboarded into the new ecosystem.

⚙️ Engineering Best Practices: The Validation Loop

Check Instance Membership: You cannot retrieve the participant list for a group you are not a member of. Attempting to do so will return a 404 or 403 error. Always perform a pre-flight check to ensure your instance is present in the channel.
Handle Admin State Mapping: Remember that isAdmin is a state that can change at any time. Your system should not "Cache and Forget" this value. The Get Participants call should be treated as a "Live View" that expires quickly.
Webhook Synchronization: Professional systems should use a "Hybrid Model": listen for webhooks for 99% of updates, and use the Get Participants API as the "Authority" for 1% of edge cases or system re-initializations.

🎯 Conclusion: Mastering the Art of the Populated Community

The Get Participants endpoint is the "Census Bureau" of your community architecture. It is your most powerful tool for understanding your audience, enforcing security, and personalizing the conversational experience at scale. By treating the participant list as a dynamic, programmable map of authority and identity, you build a conversational ecosystem that is resilient, compliant, and always perfectly targeted. You move beyond "Sending Messages into a Void" and into the world of Structured Demographic Orchestration, where every interaction is informed by exactly who is listening and who has the power to lead.

Request Parameters

Configure the parameters required to interact with this endpoint. All query and body arguments are listed below with their details.

URL Parameters

Passed in the URL query string

	`string`		Your unique WhatsApp Instance ID Example:
	`string`		Your API Access Token Example:
	`string`		The unique ID of the group Example:

Request Samples

Use these ready-to-go code snippets to integrate our API into your project quickly and efficiently. Choose your preferred language and library.

1const baseUrl = "https://api.wawp.net";
2const endpoint = "/v2/groups/1234567890@g.us/participants";
3const params = new URLSearchParams({
4  "instance_id": "123456789",
5  "access_token": "123456789"
6}).toString();
7
8
9fetch(`${baseUrl}${endpoint}${params ? '?' + params : ''}`, {
10  method: "GET",
11  headers: { "Content-Type": "application/json" },
12  
13})
14  .then(async (response) => {
15    if (response.ok) {
16      const data = await response.json();
17      console.log("Success:", data);
18      return data;
19    }
20    
21    // Error Handling
22    
23
24    const errorText = await response.text();
25    console.error(`Error ${response.status}: ${errorText}`);
26  })
27  .catch((error) => console.error("Network Error:", error));

Interactive SamplesUTF-8

Ln 27, Col 1javascript

Expected Responses

Explore all possible responses and outcomes from the server. We have documented each status code with data examples to make success and error handling easier.

Participants retrieved

application/json

object *

Example

{
"0": {
  "id": "1234567890@c.us",
  "isAdmin": true,
  "isSuperAdmin": false
  }
}

Previous TopicInvalidates the current group invite code and generates a new one

Next TopicAdd participants